The cornerstone of collaborative development
Git is a software version control system that enables distributed collaboration of engineers working all over the world. It allows for …
Overview
Recent Reviews
Awards
Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
Reviewer Pros & Cons
Pricing
Entry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Would you like us to let the vendor know that you want pricing?
5 people also want pricing
Alternatives Pricing
What is GitHub?
GitHub is a platform that hosts public and private code and provides software development and collaboration tools. Features include version control, issue tracking, code review, team management, syntax highlighting, etc. Personal plans ($0-50), Organizational plans ($0-200), and Enterprise plans…
What is Liquibase?
Liquibase is a database change management tool that helps teams release software faster and safer by bringing the database change process into existing CI/CD automation. According to the 2021 Accelerate State of DevOps Report, elite performers are 3.4 times more likely to incorporate database…
Product Demos
Git Merge and Rebase Demo
YouTube
Git hooks, practical uses (yes, even on Windows)
YouTube
Git Tutorial For Beginners | What is Git and GitHub? | Git Tutorial | DevOps Tutorial | Simplilearn
YouTube
Git Push Command | Git Bash Tutorial | Git Commands | Git Tutorial For Beginners | Simplilearn
YouTube
Product Details
- About
- Tech Details
What is Git?
Git Technical Details
| Operating Systems | Unspecified |
|---|---|
| Mobile Application | No |
Comparisons
Compare with
Reviews and Ratings
(74)
Community Insights
TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!
- Business Problems Solved
- Recommendations
Git is a widely used version control system that offers a range of use cases for different teams and organizations. Engineering and dev-ops teams rely on Git to handle version control of codebases, allowing them to create branches for features and bug fixes. By using Git, they can easily merge and release code to different environments, ensuring smooth software development processes.
Freelance software developers also find value in Git as it enables them to work on multiple machines and platforms, providing flexibility and backup of source code. They appreciate the ability to easily manage and track changes in their codebase, ensuring effective collaboration with clients and the ability to revert back if needed.
Organizations benefit from Git's ability to store source code across multiple repositories and branches. They typically have a mainline development branch for code review and automated builds, allowing for efficient management of projects. Git addresses the problem of multiple people updating a codebase by managing merging of changes, storing committed changes in a log for review, and offering rollback options when necessary.
Furthermore, Git fosters collaboration and code contribution among developers by preventing conflicts and facilitating efficient software development. It is successfully utilized by various departments like Tech Writing and Implementation, helping streamline release cycles and integrating smoothly with other tools like Bitbucket for pull requests.
Additionally, Git is an essential tool for managing app development processes. Its usage ensures faster release of changes while minimizing negative impacts on existing functionalities. Many companies rely on Git to manage massive codebases and enable cross-team code review, making it a reliable solution for tracking project progress and ensuring software security vulnerabilities are addressed.
Overall, Git's ease of use and cleaner approach to version control have received praise from users. It is widely recognized as stable and reliable for managing code, providing a centralized area for sharing and collaborating on projects across different teams.
In summary, whether it's handling version control, managing projects for customers, tracking changes in websites or internal scripting projects, or enabling concurrent work, Git proves to be a valuable and versatile tool for developers, freelancers, and organizations alike.
Users commonly recommend learning Git thoroughly to utilize its benefits for code repository management, version control, and team collaboration. They emphasize the importance of utilizing the command line interface and following established processes for branching and merging. Users also encourage exploring advanced features, seeking support from online resources like Stackoverflow, and considering other alternatives if needed. Overall, users consider Git to be an essential tool with excellent features and community support in the software development realm.
Attribute Ratings
Reviews
(1-11 of 11)Companies can't remove reviews or game the system. Here's why
June 28, 2021
Git has everything you need for code
Git is used across the organization for version control of the code build. It helps us track our deployments and snapshots of various artifacts we develop. All kinds of programming languages and files are checked in to git via github. We also control the code migration between various environments using Git.
- Pull requests to control what's checked in where
- 2-step commit and push to enable cleaner check-in process
- Personal forks to help developers with quick development and testing
- I feel that code merging using command line is not very straightforward when there are conflicts
January 30, 2020
Using Git for 5+ years
We use Git in our entire organization for our codebase versioning/management. We migrated from TortoiseSVN. We work in different teams so every team takes the branch from production/master and works in their own branch so that it should not affect any other's work.
- Fastest Branches Switching, in fractions of seconds we can switch between branches.
- Easy to pull/push code.
- When some thing went wrong on production, we have to create the revert of the pervious commit, so after fixing the issue we need to revert it again so that the original changes can apply, some times a chain of reverts continue. :(
November 23, 2019
Mandatory tool for Software Development
Our whole company uses Git for code collaboration where a team can continuously develop features for the software. Also, it allows our peers to review the code and once necessary approvals are received, we can merge the code ensuring proper workflow is followed. Git gives us helpful insight regarding project progress, software security vulnerabilities.
- It's a great version control system helps us to develop the software incrementally releasing stable versions.
- Git gives proper reminders when ever the my peers requests code review approval.
- Git can be easily integrated with other software like Slack, Developer workbenches like Web Storm, Visual Studio Code, etc.
- Git commands are very intuitive, makes us to easily understand and get the work done.
- Git gives us great insights on the project progress like the number of Pull Requests Raised, Closed Issues, etc.
- Git gives an intuitive UI, so the user can operate through the web.
- Git can still improve UI design.
- Git can also embed some artificial intelligence, and suggest alternate ways to solve the problem when the code review happens.
- Git can also suggest when the deadline for any reviews should be closed so it helps the developers in the team to finish that PR within time.
May 05, 2019
Great version control tool
Git is being used by the whole enterprise right now. We use it as a version control tool to help our developers manage their code version for better collaboration. Our developers love it and have had a great experience with it.
- Easy to use version control.
- Pull and push your code without worrying about messing others' codes.
- Great support community.
- It's kind of hard to get hands-on.
- The Error report is not very specific.
- Code conflict resolving can be a pain.
March 30, 2019
The version control system you need!
Git is one of the source code version control tools used at my organization. We are using Git (Gitlab) to store our source code across multiple repositories. We have a mainline development branch which all our new code is eventually pushed to after being code reviewed by their branch using pull requests.
- Ability to create branches and merge those changes in.
- Diff-ing changes.
- Many different GUIs, many people.
- Understanding Git has a little bit more of a learning curve when compared to other source control solutions.
February 12, 2019
Git things done
In our organization, Git is used by several departments for file versioning, collaborative work on the same source code, change tracking, branch merging, version comparison etc. Especially because we have distributed teams all over the world, we needed a reliable tool to achieve these goals, and Git was the natural choice.
- File versioning - easy to see the history of the changes.
- Collaborative work on the same source code -- by providing the ability to create branches.
- Merging branches and comparing versions made easy.
- It is free and open source.
- Git is so popular that when hiring, it is easy to find developers who already know this.
- To use Git at its full capabilities, one needs to spend some time learning it.
- Command line usage may be an issue to developers used more with GUIs. For those, you may need to add a free GUI or purchase something like Bitbucket.
- Merging code when there are conflicts can be difficult sometimes from the command line.
- Git may have bundled in more features that it needs. Most people just need the basics: pull, edit, push, merge.
February 04, 2019
Git: a solid version control tool
Git is our core version control tool in my company and it is used not only in our development department but in multiple other departments like Tech Writing and Implementation. In development, we use Git to track our development changes and to organize our release cycles with different branches to track our stages. We utilize tools that integrate with Git like Bitbucket to have a front end UI that helps us manage things like pull requests, which are branches off of QA for development changes we would like to add to release. Git is the core infrastructure in what we do here and I have been using it every day for the past 6 years.
- Ability to create branches off current releases to modify code that can be tested in a separate environment.
- Each developer had their own local copy of branches so it minimizes mistakes being made.
- Has a user-friendly UI called Git Gui that users can use if they do not like using the command line.
- Conflicts are displayed nicely so that developers can resolve with ease.
- Sometimes conflicts arise over white space which can be annoying.
- You cannot do any advanced features in the built-in GUI, you have to use an application like Bitbucket for these things.
- It can have a very high learning curve for new users because there are so many commands and things you can do that it gets very complex very fast.
September 12, 2018
Git is the king for a reason
Git is being used by our organization on an information technology department level. We use Git as our sole Version Control system for all of our software releases, maintenance & deployment.
- Git is designed to work in a distributed manner, allowing each developer to run a local node that has full control of the project. Through this, the developer is able to merge his work with others on a main 'branch' & work in sync without having to worry about stepping on your other developers toes.
- Because Git has solved the software problem of dependency, users who commit code that needs to be deleted can just roll back to a restore point, saving precious development time & tons of headaches for Information Technology. This is also very helpful when cloning projects or creating new features on the current project.
- Git has a beautiful command line interface that is intuitive, easy to learn & extensible. You can also observe all the changes you have made in your project throughout the development with just a few simple commands. This diverse set of command-line tools is easy for the end user & very powerful.
- There is currently no way to avoid downloading the entire commit history of a repository into the local copy - this can be problematic when cloning projects that have a history of many working submodules & packages.
- Advanced configurations (managing multiple branches, having commands that take 2+ arguments) can sometimes be overwhelming for inexperienced users & there is definitely a learning slope for new developers.
- You have to be precise when you use your git commands. The nature of Git commands are powerful. So powerful that if you don't know what you are doing and accidentally type a wrong command, you can cause irrevocable damage to your repository & others.
March 15, 2018
Git - the new Subversion
Git is one of the source code version control tools used at my organization (the other major one being Subversion). We are using Git to store our source code across multiple repositories and branches (features and bugs). We have a mainline development branch which all our new code is eventually pushed to, after being code reviewed by their branch using pull requests. The development branch in our Git repositories are polled for any changes, and builds are automatically run to verify the code.
- Branching
- What I find as the main benefit of Git is the ease that branches can be created in a repository - whether that's for working on new features or to fix bugs. It's as easy as selecting the code you want to branch from and "git checkout -b newBranch". Mainly I use this for branching from our development branch (also known as trunk) and once the code is finished, we merge the branch back into the development branch. Switching branches in Subversion is a little bit more complex, whereas Git is super easy to use.
- Pull Requests
- Pull requests can be created on a repository allowing code to be reviewed before being merged to the main branch. External tools like Bitbucket can be used to integrate into the Git repositories, allowing users to easily review and comment on your pull requests.
- Local Repositories
- When you use Git, you checkout the repository to your machine locally - and any commits that you make only affect your local repository, rather than the "real" repository at a remote location. This allows you to commit often and finalize all of your code before merging onto the latest development branch.
- Understanding
- Git has a little bit more of a learning curve when compared to other source control solutions, e.g. Subversion - but this is due to the more complex features it offers.
- IDE Support
- There aren't as many plugins for Git when compared to other source control solutions. Subversion has better plugins for IDEs and seems to be well supported.
- Git Bash
- Using Git bash, or the GUI that comes with Git can be slightly daunting at first. Tools like SourceTree are a solution to this problem, as they run the underlying Git commands for you.
March 01, 2018
Git - A Required Tool for All Development Teams
We are currently using Git for all of our marketing websites. We're using it to save versions of code as a backup, to track changes and to see when changes were made and by whom. It helps us track updates for our clients and enables our team to work on the same sites concurrently.
- Code backups
- Code tracking
- Branching
- Team development
- Git has a learning curve
December 14, 2017
Better choose Git!
We are using Git to store our source code with all of our clients. All the technical staff uses Git as a CVS. It's an awesome product for versioning and managing source code no matter what programming language you use.
- Versioning
- Revision of newly implemented code by using Pull Requests
- Branches to allow developer working in different features at the same time
- Good integration with CI and CD tools
- A lot of plugins and tooling are available to be integrated with Git
- Not sure, it has been working awesome to solve our needs and there is a lot of documentation available to meet the product. As you study features you discover ways to use them.